Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

build(deps): update semantic-release (major) #459

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

build(deps): update semantic-release (major) #459

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 14, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/commit-analyzer ~11.1.0 -> ~13.0.0 age adoption passing confidence
@semantic-release/github ~9.2.0 -> ~11.0.0 age adoption passing confidence
@semantic-release/npm ~11.0.0 -> ~12.0.0 age adoption passing confidence
@semantic-release/release-notes-generator ~12.1.0 -> ~14.0.0 age adoption passing confidence

Release Notes

semantic-release/commit-analyzer (@​semantic-release/commit-analyzer)

v13.0.0

Compare Source

Bug Fixes
  • log the raw message again (e2f5d6c)
Features
  • support latest conventional-changelog packages (0254d7a)
BREAKING CHANGES
  • by supporting the latest major versions of conventional-changelog packages, we are
    dropping support for previous major versions of those packages due to the breaking changes between
    majors. this only impacts your project if you are installing alongside semantic-release, so updating
    those packages to latest version should be the only change you need for this update. no action
    should be necessary if you are using default semantic-release config

v12.0.0

Compare Source

Features
  • exports: defined exports to point at ./index.js (f3358dd)
  • node-versions: dropped support for node v18 and v19 (0a23b82)
BREAKING CHANGES
  • exports: exports has been defined, which prevents access to private apis (which arent
    intended for consumption anyway)
  • node-versions: node v18 and v19 are no longer supported
semantic-release/github (@​semantic-release/github)

v11.0.0

Compare Source

chore
  • update peer dependency for semantic-release (95c7cdd)
Code Refactoring
  • modify commit associatedPRs and relatedIssues label property data type. (718134a)
Features
  • integrate warn in fail script (7a9914a)
  • integrate warn in success script (792720d)
BREAKING CHANGES
  • the commit associatedPR and relatedIssues label prop is now an array of objects with more properties
  • the minimum required version of semantic-release to use
    @​semantic-release/github is now v24.1.0

v10.3.5

Compare Source

Bug Fixes
  • replace searchAPI usage with GraphQL in findSRIssue util (#​907) (7fb46a3)

v10.3.4

Compare Source

v10.3.3

Compare Source

Bug Fixes
  • Revert: feat: verify OAuth scopes of classic GitHub PATs (#​915) (990bd73)

v10.3.2

Compare Source

Bug Fixes
  • missing "PullRequest".canBeRebased field on GHES graphql api (#​913) (4393578)

v10.3.1

Compare Source

Bug Fixes
  • max_node_limit_exceeded error when fetching associatedPRs (#​912) (bb806af)

v10.3.0

Compare Source

Features
  • allow conditional skip on success and fail comments (#​874) (e097d1c)

v10.2.0

Compare Source

Features

v10.1.7

Compare Source

Bug Fixes

v10.1.6

Compare Source

v10.1.5

Compare Source

Bug Fixes

v10.1.4

Compare Source

Bug Fixes
  • docs: correct docs branch for fail-comment links (#​893) (b591730)

v10.1.3

Compare Source

Bug Fixes

v10.1.2

Compare Source

Bug Fixes

v10.1.1

Compare Source

Bug Fixes
  • invalid GraphQL query generated when no release commits are found (#​876) (8ee2744)

v10.1.0

Compare Source

Features

v10.0.7

Compare Source

Bug Fixes
  • replace github search api with graphql in success lifecycle method (#​857) (be394cf)

v10.0.6

Compare Source

Bug Fixes
  • corrected homepage link in package.json so the generated links in the errors are valid (#​848) (865762d)

v10.0.5

Compare Source

Bug Fixes

v10.0.4

Compare Source

Bug Fixes
  • introduce dedicated option for GitHub API endpoint (#​829) (908ff83)

v10.0.3

Compare Source

v10.0.2

Compare Source

Bug Fixes

v10.0.1

Compare Source

Bug Fixes

v10.0.0

Compare Source

Features
  • node-versions: dropped support for node v18 and v19 (#​797) (aea314f)
BREAKING CHANGES
  • node-versions: node v18 and v19 are no longer supported
semantic-release/npm (@​semantic-release/npm)

v12.0.1

Compare Source

Bug Fixes
  • deps: update dependency execa to v9 (9ac5ed0)

v12.0.0

Compare Source

Features
  • exports: defined exports to point at ./index.js (9e193c2)
  • node-versions: dropped support for node v18 and v19 (2df962b)
BREAKING CHANGES
  • exports: exports has been defined, which prevents access to private apis (which arent
    intended for consumption anyway)
  • node-versions: node v18 and v19 are no longer supported
semantic-release/release-notes-generator (@​semantic-release/release-notes-generator)

v14.0.1

Compare Source

Bug Fixes

v14.0.0

Compare Source

Features
BREAKING CHANGES
  • by supporting the latest major versions of conventional-changelog packages, we are dropping support for previous major versions of those packages due to the breaking changes between majors. this only impacts your project if you are installing alongside semantic-release, so updating those packages to latest version should be the only change you need for this update. no action should be necessary if you are using default semantic-release config

v13.0.0

Compare Source

Features
  • exports: defined exports to point at ./index.js (5655b18)
  • node-versions: dropped support for node v18 and v19 (e65959a)
BREAKING CHANGES
  • exports: exports has been defined, which prevents access to private apis (which arent
    intended for consumption anyway)
  • node-versions: node v18 and v19 are no longer supported

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from wopian March 14, 2024 22:57
@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 14, 2024 •
edited
Loading

yarn.lock changes

Click to toggle table visibility
Name Status Previous Current
@semantic-release/commit-analyzer UPDATED 12.0.0 13.0.0
@semantic-release/github UPDATED 10.3.5 11.0.0
@semantic-release/release-notes-generator UPDATED 13.0.0 14.0.1
conventional-changelog-angular UPDATED 7.0.0 8.0.0
conventional-changelog-writer UPDATED 7.0.1 8.0.0
conventional-commits-filter UPDATED 4.0.0 5.0.0
conventional-commits-parser UPDATED 5.0.0 6.0.0
deprecation REMOVED 2.3.1 -
meow UPDATED 12.1.1 13.2.0

@renovate renovate bot changed the title build(deps): update devdependency @semantic-release/github to ~10.0.0 build(deps): update semantic-release (major) Mar 16, 2024
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 5 times, most recently from 4173e78 to 5d358e0 Compare March 21, 2024 02:02
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 5 times, most recently from b53092e to ac18e48 Compare March 30, 2024 09:08
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from 857b253 to 596357b Compare April 8, 2024 01:43
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from d9d7957 to d19a7bf Compare April 22, 2024 04:31
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 6 times, most recently from 5ad8f0d to 1b2718d Compare May 6, 2024 00:08
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 4 times, most recently from e2ca98b to 8d87b00 Compare May 13, 2024 05:00
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from 8d87b00 to 0730d54 Compare May 23, 2024 07:52
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 3 times, most recently from cb05348 to 869737b Compare August 9, 2024 23:27
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 4 times, most recently from 4b71b08 to 3d4bfd8 Compare August 19, 2024 01:49
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 5 times, most recently from 6d8584d to d62caa8 Compare August 27, 2024 13:09
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 3 times, most recently from dd45553 to 9e3b153 Compare September 3, 2024 14:37
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 3 times, most recently from 7a668b8 to be42b2b Compare September 14, 2024 18:20
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from 8b94019 to ab8b8e2 Compare September 23, 2024 03:30
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 4 times, most recently from 00c1e7d to 0d2f0ec Compare September 30, 2024 04:12
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from cdddf2c to ac0a39c Compare October 7, 2024 03:59
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from 0d5420a to f8a14a1 Compare October 18, 2024 21:18
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from f8a14a1 to 8062f79 Compare October 21, 2024 03:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@wopian wopian Awaiting requested review from wopian

Assignees

@wopian wopian

Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@wopian